Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Don't delete local shard data when its allocated on a node that doesn't exists #4502

Closed
kimchy opened this issue Dec 18, 2013 · 0 comments
Closed

Don't delete local shard data when its allocated on a node that doesn't exists #4502

kimchy opened this issue Dec 18, 2013 · 0 comments
Labels
>bug v0.90.8 v1.0.0.RC1

Comments

@kimchy
Copy link
Member

kimchy commented Dec 18, 2013

This is an extreme case, exposed by a bug we had in our allocation in local gateway, causing a cluster state that doesn't include a node in the nodes list, but still has the shard in the routing table pointing at the non existent node. Then, when a node on the same box comes back, it will cause the local shard data to be deleted because it thinks its fully allocated on other nodes.
@kimchy kimchy closed this as completed in f0356b2 Dec 18, 2013
kimchy added a commit that referenced this issue Dec 18, 2013
@kimchy
Don't delete local shard data when its allocated on a node that doesn…
296f44e 
…'t exists

This is an extreme case, exposed by a bug we had in our allocation in local gateway, causing a cluster state that doesn't include a node in the nodes list, but still has the shard in the routing table pointing at the non existent node. Then, when a node on the same box comes back, it will cause the local shard data to be deleted because it thinks its fully allocated on other nodes.
fixes #4502
brusic pushed a commit to brusic/elasticsearch that referenced this issue Jan 19, 2014
@kimchy @brusic
Don't delete local shard data when its allocated on a node that doesn…
bc3a9f7 
…'t exists

This is an extreme case, exposed by a bug we had in our allocation in local gateway, causing a cluster state that doesn't include a node in the nodes list, but still has the shard in the routing table pointing at the non existent node. Then, when a node on the same box comes back, it will cause the local shard data to be deleted because it thinks its fully allocated on other nodes.
fixes elastic#4502
mute pushed a commit to mute/elasticsearch that referenced this issue Jul 29, 2015
@kimchy
Don't delete local shard data when its allocated on a node that doesn…
d7fc455 
…'t exists

This is an extreme case, exposed by a bug we had in our allocation in local gateway, causing a cluster state that doesn't include a node in the nodes list, but still has the shard in the routing table pointing at the non existent node. Then, when a node on the same box comes back, it will cause the local shard data to be deleted because it thinks its fully allocated on other nodes.
fixes elastic#4502
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
>bug v0.90.8 v1.0.0.RC1
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@kimchy